@rubytech/create-maxy 1.0.698 → 1.0.700

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.698",
+  "version": "1.0.700",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/neo4j/schema.cypher

@@ -259,8 +259,8 @@ ON EACH [k.summary, k.content];
 
 // ----------------------------------------------------------
 // Conversation node — persistent conversation sessions
-// One Conversation per sessionKey. Scoped to an account via
-// (Conversation)-[:BELONGS_TO]->(LocalBusiness).
+// One Conversation per sessionKey. Account scope is encoded by the
+// `accountId` property on the node itself — every read filters by it.
 // Public conversations carry a visitorId (browser cookie) and
 // agentSlug for session resume across page reloads and server restarts.
 // Task 621 — carries a `summary` string denormalised from the first
@@ -463,8 +463,9 @@ FOR (sr:StepResult) ON (sr.runId);
 
 // ----------------------------------------------------------
 // UserProfile node — structured knowledge about the business owner
-// Platform-native (no Schema.org equivalent). One per account.
-// Linked via (UserProfile)-[:BELONGS_TO]->(LocalBusiness).
+// Platform-native (no Schema.org equivalent). One per (accountId, userId).
+// Linked via (AdminUser)-[:HAS_PROFILE]->(UserProfile). Account scope is
+// encoded by the `accountId` property on the node itself.
 //
 // Created automatically on first admin session start via MERGE.
 // Properties populated progressively through conversation and
@@ -717,3 +718,31 @@ FOR (n:Trashed) ON (n.accountId);
 
 CREATE INDEX trashed_at IF NOT EXISTS
 FOR (n:Trashed) ON (n.trashedAt);
+
+// ----------------------------------------------------------
+// Person.linkedinUrl — natural key for LinkedIn-origin Persons.
+// Indexed (not uniquely constrained) so a Person can appear
+// first from another source (email-first) and later have its
+// linkedinUrl filled in without collision. Schema-base requires
+// `email or telephone` on :Person, but LinkedIn basic exports
+// rarely emit either for connections; `linkedinUrl` is the
+// reliable dedup key for the linkedin-import skill.
+// ----------------------------------------------------------
+CREATE INDEX person_linkedin_url IF NOT EXISTS
+FOR (p:Person) ON (p.linkedinUrl);
+
+// ----------------------------------------------------------
+// Credential — schema:EducationalOccupationalCredential.
+// Professional certifications (e.g. LinkedIn's Certifications.csv,
+// or credentials entered through memory-write). Natural key is
+// the triple (accountId, name, authority) — a credential is
+// identified by what it is and who issued it, within a tenant.
+// No existing Maxy label covers this semantics, so a new label
+// is warranted (unlike articles → :CreativeWork, recommendations
+// → :Review, skills → :DefinedTerm, which all reuse existing labels).
+// ----------------------------------------------------------
+CREATE CONSTRAINT credential_unique IF NOT EXISTS
+FOR (c:Credential) REQUIRE (c.accountId, c.name, c.authority) IS UNIQUE;
+
+CREATE INDEX credential_account IF NOT EXISTS
+FOR (c:Credential) ON (c.accountId);

package/payload/platform/plugins/docs/references/deployment.md

@@ -65,6 +65,7 @@ The logs will show which service failed to start and why. Common causes:
 - **Neo4j not started** — run `sudo systemctl start neo4j` and retry
 - **Port 19200 already in use** — check for another process: `lsof -i :19200`
 - **Claude OAuth expired** — the next admin session will prompt you to re-authenticate
+- **NEO4J_URI port mismatch** — the admin agent throws `port :X disagrees with brand.json neo4jPort :Y`. Edit `NEO4J_URI` in `~/{configDir}/.env` to match the brand's declared `neo4jPort`, or correct `neo4jPort` in `brand.json` and reinstall. (Task 681)
 
 ## Systemd units on each device
 

package/payload/platform/plugins/docs/references/graph.md

@@ -36,3 +36,19 @@ the filter popover to surface them; they render with a faded fill and dashed
 border, with their zoom-tier labels intact. The `N msgs` count excludes
 trashed Messages, so the detailed-tier label reflects only live turns in the
 conversation.
+
+## Agent-execution telemetry
+
+`ToolCall`, `StepResult`, `WorkflowStep`, and `WorkflowRun` nodes are
+agent-execution telemetry — kept for audit but noisy for day-to-day graph
+navigation (they make up roughly 9% of a typical brand's live nodes).
+They are hidden from `/graph` by default. To see them — for audit, debug,
+or tracing a specific agent run — open the filter popover and tick
+**Include agent actions** (the checkbox directly below **Show trashed**).
+Flipping it on surfaces the four labels as chips in the popover roster AND
+keeps them on the canvas when you pivot into a neighbourhood. The toggle
+is session-scoped: every new session starts with agent actions hidden, so
+the 90% domain-navigation path stays clean without having to remember to
+switch them off. Flipping it off again also drops them from any already-
+expanded neighbourhood so a click near a `ToolCall` does not re-introduce
+it.